Fix: TypeScript root detection to support Python project markers - #39
Merged
Conversation
dejo1307
approved these changes
Jun 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fix TypeScript extractor's detection of deep/nested projects by extending the heuristics to recognize Python project markers (pyproject.toml, setup.py, setup.cfg, requirements.txt). This ensures the TS root search uses a deeper recursion depth for repos that are multi-language or deeply nested Python projects.
Changes
internal/extractors/tsextractor/ts.goisJavaStructured()→isDeepNestedProject()pom.xml,build.gradle,build.gradle.ktspyproject.toml,setup.py,setup.cfg,requirements.txtisDeepNestedProject()returns true,maxDepthis increased from 2 to 8Why
Previously the extractor only treated Java projects as "deeply nested" and increased search depth accordingly. That missed Python monorepos or repositories with deeply nested TS/JS code under Python projects, causing the TS extractor to stop searching too early and fail to locate the TypeScript root.
Adding common Python markers makes the extractor more robust in multi-language repositories and monorepos.